Skip to content

feat(build): add noop BuildManager implementation#168

Closed
behinddwalls wants to merge 1 commit into
preetam/build-extfrom
preetam/build-noop
Closed

feat(build): add noop BuildManager implementation#168
behinddwalls wants to merge 1 commit into
preetam/build-extfrom
preetam/build-noop

Conversation

@behinddwalls
Copy link
Copy Markdown
Collaborator

@behinddwalls behinddwalls commented May 29, 2026

Summary

Adds extension/build/noop, the first implementation of the
build.BuildManager interface. It performs no real work: Trigger
hands back a unique build ID and BuildStatusSucceeded without
contacting any provider, Status always reports succeeded, and
Cancel/Close are no-ops. An atomic counter generates unique IDs
and keeps the type safe for concurrent use.

Intended as a stub for wiring tests and as a best-case baseline where
every build passes instantly — mirrors the role of
extension/conflict/none for the conflict analyzer.

Test Plan

  • ✅ `make gazelle && make fmt && make lint`
  • ✅ `make check-gazelle && make check-tidy`
  • ✅ `bazel test //extension/build/noop/...`

Issues

Stack

  1. feat(build): add BuildManager extension and trim BuildStatus enum #167
  2. @ feat(build): add noop BuildManager implementation #168
  3. feat(orchestrator): wire BuildManager into the build controller #169

@behinddwalls behinddwalls marked this pull request as ready for review May 29, 2026 22:59
@behinddwalls behinddwalls requested review from a team and sbalabanov as code owners May 29, 2026 22:59
## Summary

Adds `extension/build/noop`, the first implementation of the
`build.BuildManager` interface. It performs no real work: `Trigger`
hands back a unique build ID and `BuildStatusSucceeded` without
contacting any provider, `Status` always reports succeeded, and
`Cancel`/`Close` are no-ops. An atomic counter generates unique IDs
and keeps the type safe for concurrent use.

Intended as a stub for wiring tests and as a best-case baseline where
every build passes instantly — mirrors the role of
`extension/conflict/none` for the conflict analyzer.

## Test Plan

- ✅ \`make gazelle && make fmt && make lint\`
- ✅ \`make check-gazelle && make check-tidy\`
- ✅ \`bazel test //extension/build/noop/...\`

## Issues

(none)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant